Thanks for posting this, Christie. And thanks to Bill for addressing
this subject. I am going to have numerous views in projects that contain
some of the same themes (I am working on changing my scripts to clone
these and not just add them!). The users will be editing some of these
themes and it is very important that changes be reflected in all the
cloned themes. Does anyone know of any scripts out there that will
search through all views in a project and, based on a specified theme
name, find all themes with the same name, delete them and 're-clone'
them? I can write this myself, but just wondering if this sounds like a
reasonable way to maintain changes throughout a project? I'd appreciate
any thoughts/suggestions/ideas on this matter.

Thanks,
Jason




"Kearney, Christie" wrote:
>
> I got this e-mail from Bill Huber warning me about the avenue scripts I sent
> out. If you will be using the same scripts, please read the warning below.
> Thanks, Christie Kearney
>
> >Davoust)
> >...
> >for each elt in the_views
> >         elt.AddTheme(the_theme)
> >end
> >
> >(Jorquera)
> ...
> >   aDoc.AddTheme(aTheme)
>
> It is very important to know that these scripts contain a common nasty bug:
> because the same theme is added to all views, any changes to the theme in
> one view will occur in the versions of that theme shown in all the other
> views: changing the legend, selecting features, open the table, turning the
> theme on or off, etc.  This sounds like a nice feature, and it could be,
> except it violates the Avenue object model (themes are supposed to be
> associated with a unique view: see the Avenue help on "GetView"), which
> seems eventually to lead to unstable ArcView behavior, segmentation
> violations, and so on.  ***You could lose your project when this happens.***